Scenario #9810: The Frontend Fetches the Auth Configuration of a Fake Jwt Backend

GET /api/auth-config reports which authentication method the backend expects and which parameters a login for that method needs, so that a frontend can configure its login at runtime instead of from environment-specific configuration files distributed separately. With the fake-jwt profile active, the response reports the token-URL of the local password-grant login, which is all a client needs — the fake token endpoint accepts any credentials and involves neither a client registration nor any secrets.

Fetch the authentication configuration without any login

HTTP GET "/api/auth-config"
=> status: 200 OK 
{
  "method" : "fake-jwt",
  "authority" : null,
  "tokenUrl" : "/fake-jwt/token"
}

generated on 2026-08-10 01:38:09 for branch